ObjectDB Database Search
51-100 of 200 resultsunable to update table in slave server database
;when master server is down ,in slave server during update operation in table getting below issues. Failed ... (ObjDBem.java:75) at code.db.jpa.oodb.ObjDBem. Update (ObjDBem ... for this is that the synchronization is always in one direction, i.e. the slave is updated by the master, updating
|
|
Massive schema update
the shema update ? Thanks in advance. Best Regars, Pablo. Pablo Berra Pablo Berra The effect on performance of schema update (including using the configuration element) is minimal. After an old object is updated and stored in the database again it would not need conversion in future retrieval
|
|
Update entity without first opening a transaction
Hi everyone, I want to update an entity in my program without having to open a transaction ... should be updated immediately. How can I get this done? joelcraenhals Joël Craenhals JPA requires using transactions for updating the content of a database. But if you use Java EE or Spring, the container may manage the transactions automatically. support Support
|
|
Schema update: package, class and field
first processed the "defined" schema update and then the "automatic" schema update or ... also in future versions, since there are no plans to rewrite the schema update mechanism (which generally
|
|
How to enable and disable auto schema update?
Hello, Can I enable and disable the auto schema update ? In some cases if multiple applications ... : Instate of updating the schema with old library db should throw some error and data should not corrupt ... Maharana Hi Any update on this? the above command is not working for me. Manoj Manoj Kumar Maharana  
|
|
Schema Update large refactoring
to do an automatic schema update of our database using the objectdb.conf file. The old package structure looks like ... , if it is possible to perform some sort of wildcard schema update , instead of specifying all the thousands ... , if it is possible to perform some sort of wildcard schema update Wildcards are not supported.  
|
|
Version 2.5.6 enhancement problem solved by updating to version 2.5.7_03
After updating some of my code to java 8, enhancement threw "unexpected" exceptions from ... have been related to the java 8 update . In any event, my enhancement problem went away when I updated ObjectDB from 2.5.6.x to 2.5.7_03. Maybe this will save someone a bit
|
|
Significant I/O costs during batch update or insert data.
Our application has some complex entities. We do batch update (merge detached entity) every 2 minutes. We find the period significant IO costs these days, and disappeared when turn off the batch updating . 1.ObjectDB is in embedded mode. 2.ObjectDB version is 2.3.7 3.Database file size is nearly
|
|
Auto Date for Creation and Update
Hi, is there a way with objectdb to use annotations so that - automatically - the creation Date gets updated once only and the change Date on each change ... ? Kind regards, Thomas tlehmann Thomas Lehmann You may be able to update
|
|
updating one to many sometimes fails
we did setup automated tests for our system and it seams that in around 1 of 100 cases the update of a one to many collection is not working. Definition: @OneToMany(fetch=FetchType.LAZY) @Index ... with the information provided. To ensure reliable updates , the instance must be associated
|
|
Multiple Collection Fields not update correctly
. But when updating (merging existing record) somehow the rotation overrides the position. I
|
|
Getting Unexpected internal exception when updating entity in MEM db
.java:307) at org.vn.radius.cc.server.db.RtDB. Update (RtDB.java:101) ... 10 more Caused by: java.lang
|
|
Update Entity references if we change the type of an entity
will be committed. So after the database update your application can be used with this option
|
|
Internal exception when updating date filed (TemporalType.DATE)
Hello! ObjectDB version 2.5.3_02. I get internal exception when commiting update Date field (javax.persistence.TemporalType.DATE). [ObjectDB 2.5.3_02] javax.persistence.RollbackException Failed to commit transaction: (error 613) at com.objectdb.jpa.EMImpl.commit(EMImpl.java:290
|
|
Schema Update: class hierarchy change
build 2.6.3_02 that should fix this issue. support Support Thanks for the Update . Now it works
|
|
schema update procedure
Is there a specific procedure that we should follow when making schema updates ? I have often found that it takes several restarts of the the server to complete the change. The issue is that there may be changes in many places. Each change appears to be applied as the class is first encountered
|
|
Indexes broken after schema update.
Anyone else noticed this? I updated an entity Object with some new fields, restarted the database to pick up the new schema and now none of the indexes work, except the @Id. I can query by any field that is not indexed on the existing Object but as soon as I try and query against a field
|
|
Schema-Update: Rename superclass and remove one subclass
Schema-Update: Rename superclass and remove one subclass
|
|
Unable to update a OneToMany Set
Unable to update a OneToMany Set
|
|
NPE after an @embedded obj is updated for a detached entity
NPE after an @embedded obj is updated for a detached entity
|
|
Bidirectional OneToMany is slow on updated items
Bidirectional OneToMany is slow on updated items
|
|
Is there an update on running ObjectDB purely in-memory?
Is there an update on running ObjectDB purely in-memory?
|
|
Exception after update of indices of Entity class
Exception after update of indices of Entity class
|
|
Best practice: Database update/migration of embedded databases in products
Best practice: Database update/migration of embedded databases in products
|
|
A few entities loss after update to 2.3.7_08!
A few entities loss after update to 2.3.7_08!
|
|
Entity object parameter in Explorer parameter
Hello, I cannot set an entity object in a parameter for a bulk update in the explorer query ... parameter for an update ? Any time that I need to do a bulk update , I need to compile a special ... the SET clause. For example, in the query: UPDATE Account dep SET dep.status=:a WHERE dep.status=:b
|
|
Pessimistic Lock Timeouts setting
. My situation is where many clients from 1 company are accessing the same counter when bulk ... on stale updates . Willks William Support of pessimistic lock timeout setting ( javax.persistence ... to update object com.x.y.z.ProductCodeTracking:1 - locked by another owner (error 672) And finally
|
|
Update query bug
Some code. Problem in UPDATE query. TypedQuery query = (TypedQuery ) em.createQuery("SELECT t FROM ... ) attributeValue); list.add(temp); TypedQuery query2 = (TypedQuery ) em.createQuery(" UPDATE Person p SET p ... This UPDATE query is invalid because JPQL UPDATE queries are limited to setting values not
|
|
jakarta.persistence.criteria.CommonAbstractCriteria
and subqueries as well as to update and delete criteria operations. It is not intended to be used directly in query construction. Note that criteria queries and criteria update and delete operations are typed differently. Criteria queries are typed according to the query result type. Update
|
|
unclear syntax for update query
the syntax for selective update is unclear as the syntax in the documentation seems to be wrong. Query Update Action Set transferred = 0 where a.objectsInCharge.nodePath like "/(PR)W4455NS01 ... ===================== Unexpected query token 'a' Update Action Set transferred = 0 where == a
|
|
UPDATE statemen crash when i put the WHERE clause.
Hello, i have a problem with a UPDATE statement. When i run the code without WHERE clause the cod ... ().begin() ; updateEm.createQuery( " update Record as n set n.lab_points=:points where n.student.nume=:nume ... this update query is not supported, but a better error message is required. If you can post the full stack
|
|
ObjectDB BIRT Driver Update
is fixed for all 2.x versions. However, since the client-server protocol is occasionally being updated ... if there is no match. There is a report of an exception on attempt to update the ObjectDB BIRT plugin in ... ObjectDB server versions, and maybe also help with updating the plugin in an existing Eclipse workspace
|
|
Schema-Update: Deactivation of automatic entity class removing and introduction of a new class remove in the schema config
with our update concept, because it would be a very big effort to recognize data of plugins in ... classes. We appreciate the other features of the automatic schema update very much. btc_es BTC ... more limitations like this. UPDATE : The described scenario works only with enhanced entities
|
|
boolean field flips after schema update (in class) of another field
updated the ObjectDB version once or twice. itsme Martin Petzold That mentioned issue does not ... . support Support Any updates regarding this issue? Did it happen again? Have you switched to version 2.8 ... or testing environment. itsme Martin Petzold Thank you for the update . No argue
|
|
selective update not working
we try to optimize for our queries and tried a selective update , but in explorer it just shows query execution error: UPDATE ObjectNode o SET o.state = 5 where o.classIdentifier = '(MA ... ), which is not allowed in UPDATE queries. See this stackoverflow thread for a more detailed explanation. support Support
|
|
Collection update does not increase entity version and is not persisted
increase and the updated event is not stored in the database (retrieve the event shows ... () { if (attachments == null) attachments = new ArrayList (); return attachments; } and update  
|
|
Indexes broken after schema update
was updated , etc.). support Support I'll dig up the change revision for the entity so I can work
|
|
Deadlock on Schema Update during Multithreading activity
Deadlock on Schema Update during Multithreading activity
|
|
jakarta.persistence.ForeignKey
: FOREIGN KEY ( {, } ... ) REFERENCES [ ( {, } ... ) ] [ ON UPDATE ] [ ON DELETE ... will generate foreign key constraints whose update and delete actions it determines most appropriate ... element is not specified, the provider will generate a constraint whose update and delete actions
|
|
jakarta.persistence.FlushModeType
TypedQuery object, the persistence provider is responsible for ensuring that all updates to the state ... this by flushing updates to those entities to the database or by some other means. On the other hand, if COMMIT is set, the effect of updates made to entities in the persistence context on queries
|
|
jakarta.persistence.Version
or timestamp fails during an attempt to update the entity, that is, if the version or timestamp held in the database changes between reading the state of an entity instance and attempting to update or ... ; This field declares a revision timestamp: @Version @Column(name = "LAST_ UPDATED ") private Instant
|
|
jakarta.persistence.Column
public String getDescription() { return description; } Example 3: @Column(name = "ORDER_COST", updatable ... Since: Jakarta Persistence (JPA) 1.0 boolean updatable (Optional) Whether the column is included in SQL UPDATE statements generated by the persistence provider. Default: true Since: Jakarta Persistence
|
|
jakarta.persistence.StoredProcedureQuery.getUpdateCount()
() Return the update count or -1 if there is no pending result or if the next result is not an update count. Returns: update count or -1 if there is no pending result or if the next result is not an update count. Throws: PersistenceException - if the query execution exceeds the query timeout value set
|
|
jakarta.persistence.StoredProcedureQuery.executeUpdate()
() Return the update count of -1 if there is no pending result or if the first result is not an update count. The provider will call execute on the query if needed. Returns: the update count or -1 if there is no pending result or if the next result is not an update count.. Throws: PersistenceException
|
|
jakarta.persistence.JoinColumn
provider. Default: true Since: Jakarta Persistence (JPA) 1.0 boolean updatable (Optional) Whether the column is included in SQL UPDATE statements generated by the persistence provider. Default: true
|
|
jakarta.persistence.MapKeyColumn
boolean updatable (Optional) Whether the column is included in SQL UPDATE statements generated by
|
|
jakarta.persistence.MapKeyJoinColumn
provider. Default: true Since: Jakarta Persistence (JPA) 1.0 boolean updatable (Optional) Whether the column is included in SQL UPDATE statements generated by the persistence provider. Default: true
|
|
jakarta.persistence.EntityManager.createQuery(CriteriaUpdate)
; CriteriaUpdate updateQuery ) Create an instance of Query for executing a criteria update query. Parameters: updateQuery - a criteria update query object Returns: the new query instance. Throws: IllegalArgumentException - if the update query is found to be invalid. Since: Jakarta Persistence (JPA) 2.1
|
|
jakarta.persistence.EntityManager.createNativeQuery(String)
Jakarta Persistence (JPA) Method in jakarta.persistence.EntityManager Query createNativeQuery ( String sqlString ) Create an instance of Query for executing a native SQL statement, e.g., for update or delete. If the query is not an update or delete query, query execution will result
|
|
jakarta.persistence.ManyToOne
= false) @JoinColumn(name = "CUST_ID", nullable = false, updatable = false) public Customer
|